The Cisco PE switch providing MPLS Virtual Private Wire Service (VPWS) must be configured to have the appropriate virtual circuit identification (VC ID) for each attachment circuit.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-221121	CISC-RT-000670	SV-221121r622190_rule		High

Description
VPWS is an L2VPN technology that provides a virtual circuit between two PE switches to forward Layer 2 frames between two customer-edge switches or switches through an MPLS-enabled IP core. The ingress PE switch (virtual circuit head-end) encapsulates Ethernet frames inside MPLS packets using label stacking and forwards them across the MPLS network to the egress PE switch (virtual circuit tail-end). During a virtual circuit setup, the PE switches exchange VC label bindings for the specified VC ID. The VC ID specifies a pseudowire associated with an ingress and egress PE switch and the customer-facing attachment circuits. To guarantee that all frames are forwarded onto the correct pseudowire and to the correct customer and attachment circuits, it is imperative that the correct VC ID is configured for each attachment circuit.

Description

VPWS is an L2VPN technology that provides a virtual circuit between two PE switches to forward Layer 2 frames between two customer-edge switches or switches through an MPLS-enabled IP core. The ingress PE switch (virtual circuit head-end) encapsulates Ethernet frames inside MPLS packets using label stacking and forwards them across the MPLS network to the egress PE switch (virtual circuit tail-end). During a virtual circuit setup, the PE switches exchange VC label bindings for the specified VC ID. The VC ID specifies a pseudowire associated with an ingress and egress PE switch and the customer-facing attachment circuits. To guarantee that all frames are forwarded onto the correct pseudowire and to the correct customer and attachment circuits, it is imperative that the correct VC ID is configured for each attachment circuit.

STIG	Date
Cisco NX OS Switch RTR Security Technical Implementation Guide	2023-02-15

Details

Check Text ( C-22836r409852_chk )
Verify that the correct and unique VCID has been configured for the appropriate attachment circuit. In the example below Ethernet2/1 is the CE-facing interface that is configured for VPWS with the VCID of 55. Step 1: Review the L2VPN virtual circuits and determine the member attachment circuit and pseudowire. l2vpn xconnect context VC55 member Ethernet2/1 member Pseudowire55 Step 2: Determine the VCID as configured for neighbor and verify the same VCID is defined on the remote PE device. port-profile type pseudowire MPLS_PROFILE encapsulation mpls interface Pseudowire55 neighbor 10.10.22.1 55 inherit port-profile MPLS_PROFILE Note: VPWS is also known as Ethernet over MPLS (EoMPLS) and Ethernet Virtual Circuit (EVC). If the correct VC ID has not been configured on both switches, this is a finding.

Check Text ( C-22836r409852_chk )

Verify that the correct and unique VCID has been configured for the appropriate attachment circuit. In the example below Ethernet2/1 is the CE-facing interface that is configured for VPWS with the VCID of 55.

Step 1: Review the L2VPN virtual circuits and determine the member attachment circuit and pseudowire.

l2vpn xconnect context VC55
member Ethernet2/1
member Pseudowire55

Step 2: Determine the VCID as configured for neighbor and verify the same VCID is defined on the remote PE device.

port-profile type pseudowire MPLS_PROFILE
encapsulation mpls

interface Pseudowire55
neighbor 10.10.22.1 55
inherit port-profile MPLS_PROFILE

Note: VPWS is also known as Ethernet over MPLS (EoMPLS) and Ethernet Virtual Circuit (EVC).

If the correct VC ID has not been configured on both switches, this is a finding.

Fix Text (F-22825r409853_fix)
Assign globally unique VC IDs for each virtual circuit and configure the attachment circuits with the appropriate VC ID.